History, Events tab (on page 1) for respective units.When you attach a unit as a Payload unit to another unit (Primary), N4 copies the following routing-related fields from the Primary unit in the Unit Combo to the Payload unit:
Carrier O/B Intended
Port of Discharge
Second Port of Discharge
Destination
In addition, if you make any changes to the above fields for the Primary unit after the Payload units are attached, N4 propagates these changes to all the Payload units in the unit combo.
When you update the routing of the Primary unit, N4 records the UNIT_REROUTE event for the Primary unit and the UNIT_PAYLOAD_REROUTE event for all the Payload units in the unit combo. You can view these events in the Unit Inspector History, Events tab (on page 1) for respective units.
N4 updates the Port of Discharge (POD) of the payload unit with the POD of the primary unit only if you update the category and POD of the primary unit at the same time using the Routing form (on page 1).
Also, when you extract the chargeable events for the Payload unit, in the Chargeable Unit Events view, the Bundle Unit ID (bexuBundleUnitId) and bexuBundleUfvGkey fields for the Payload unit are set as the Unit Nbr of the Primary unit (Related Unit Nbr).
Notes
The Payload unit inherits the routing of the Primary unit only if the Primary unit:
Has the Category = Export or Transship.
Is an IFT container with Category = Export.
Was received through the gate.
N4 does not propagate the routing from the Primary unit to the Payload units in a unit combo if the Primary unit has a Category other than Export or Transship or if the Primary will be delivered through the gate.